[CONTP-849] Fix loop detection bug and add unit tests for cluster agent leader election#43680
Conversation
3370331 to
0982106
Compare
1827ade to
6cdffc3
Compare
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 92bf342 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | -0.56 | [-3.55, +2.43] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | file_tree | memory utilization | +0.85 | [+0.78, +0.92] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.56 | [+0.51, +0.61] | 1 | Logs bounds checks dashboard |
| ➖ | docker_containers_memory | memory utilization | +0.51 | [+0.43, +0.58] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.43 | [+0.38, +0.49] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.12 | [-0.29, +0.52] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | +0.11 | [-0.12, +0.34] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | +0.08 | [-0.29, +0.45] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | +0.07 | [+0.00, +0.14] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | +0.06 | [-0.17, +0.29] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | +0.03 | [-0.02, +0.07] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.08, +0.08] | 1 | Logs |
| ➖ | otlp_ingest_metrics | memory utilization | +0.00 | [-0.15, +0.15] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | -0.00 | [-0.13, +0.12] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.14, +0.12] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.05 | [-0.43, +0.34] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | -0.15 | [-0.31, +0.02] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | -0.17 | [-0.38, +0.04] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.22 | [-0.26, -0.19] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_logs | memory utilization | -0.24 | [-0.34, -0.14] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | -0.43 | [-0.64, -0.22] | 1 | Logs bounds checks dashboard |
| ➖ | docker_containers_cpu | % cpu utilization | -0.56 | [-3.55, +2.43] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | -1.30 | [-2.75, +0.15] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -2.40 | [-2.49, -2.32] | 1 | Logs |
Bounds Checks: ✅ Passed
| perf | experiment | bounds_check_name | replicates_passed | links |
|---|---|---|---|---|
| ✅ | docker_containers_cpu | simple_check_run | 10/10 | |
| ✅ | docker_containers_memory | memory_usage | 10/10 | |
| ✅ | docker_containers_memory | simple_check_run | 10/10 | |
| ✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
| ✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | memory_usage | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
0cd8101 to
a4f612e
Compare
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
185f729 to
effca9e
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
minyi.zhu@datadoghq.com unqueued this merge request |
|
/merge --cancel |
|
View all feedbacks in Devflow UI.
|
|
/remove |
|
View all feedbacks in Devflow UI.
This merge request was already processed and can't be unqueued anymore. To get help about command usage, write If you need support, contact us on Slack #devflow with those details! |
effca9e to
8e083da
Compare
8e083da to
0169589
Compare
gabedos
left a comment
There was a problem hiding this comment.
loop detection tests look good to me
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
Build pipeline has failing jobs for 9a9eec7: What to do next?
DetailsSince those jobs are not marked as being allowed to fail, the pipeline will most likely fail. |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
…nt leader election (#43680) ### What does this PR do? - Add unit tests for cluster agent leader election and leadership transitions - Fix bug in LeaderForwarder.Forward() where loop detection didn't return after writing error ### Motivation Fixed a bug in pkg/clusteragent/api/leader_forwarder.go where loop detection (via X-DCA-Follower-Forwarded header) wrote an HTTP 508 error but continued to forward the request to the leader anyway. Added missing return statement to properly short-circuit the request. New Tests pkg/clusteragent/api/leader_forwarder_test.go - TestLeaderForwarder_SetLeaderIP - tests leader IP setting, updating, and clearing - TestLeaderForwarder_Forward_NilProxy - tests behavior when no leader is configured - TestLeaderForwarder_Forward_LoopDetection - tests that forwarding loops are properly detected and rejected - TestLeaderForwarder_Forward_WithLeader - tests successful forwarding to leader pkg/clusteragent/api/leader_handler_test.go - Enhanced fakeLeaderForwarder mock to track leader IP changes and forward calls - TestRejectOrForwardLeaderQuery_LeadershipTransition - tests behavior when leadership changes (leader → follower → leader) - TestRejectOrForwardLeaderQuery_LeaderIPChange - tests that forwarder is updated when leader IP changes during follower state ### Describe how you validated your changes ### Additional Notes Co-authored-by: minyi.zhu <minyi.zhu@datadoghq.com>
What does this PR do?
Motivation
Fixed a bug in pkg/clusteragent/api/leader_forwarder.go where loop detection (via X-DCA-Follower-Forwarded header) wrote an HTTP 508 error but continued to forward the request to the leader anyway.
Added missing return statement to properly short-circuit the request.
New Tests
pkg/clusteragent/api/leader_forwarder_test.go
pkg/clusteragent/api/leader_handler_test.go
Describe how you validated your changes
Additional Notes